Methods, systems, and media for presenting a reminder to view content

ABSTRACT

Methods, systems, and media for presenting a reminder to view content are provided. In accordance with some embodiments, a method for presenting a reminder to view content is provided, the method comprising: determining that a message that includes a link to a first content item has been received by a user device; determining whether the link to the content item has been selected; in response to determining that the link to the content item has not been selected, storing metadata associated with the content item; determining that a user is viewing a second content item that is related to the first content item; determining a probability value that indicates a likelihood that the user would be interested in viewing the first content item; and causing an interface that includes a reminder to view the first content item to be presented on the user device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/658,977, filed Oct. 21, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/057,421, filed Mar. 1, 2016, each of which ishereby incorporated by reference herein in its entirety

TECHNICAL FIELD

The disclosed subject matter relates to methods, systems, and media forpresenting a reminder to view content.

BACKGROUND

People often receive links to videos from their friends, for example, intext messages, e-mails, or instant message chats. In some instances, thetime when the message is received might not be a good time to watch thevideo. However, it can be difficult to remember to watch the video at amore convenient time.

Accordingly, it is desirable to provide new methods, systems, and mediafor presenting a reminder to view content.

SUMMARY

Methods, systems, and media for presenting a reminder to view contentare provided.

In accordance with some embodiments of the disclosed subject matter, amethod for presenting a reminder to view content is provided, the methodcomprising: determining that a message in a communication interface thatincludes a link to a first content item has been received by a userdevice; determining, at a first point in time, whether the link to thecontent item has been selected using the user device; in response todetermining that the link to the content item has not been selected,storing metadata associated with the content item in association with anidentifier of the user device; determining, at a second point in time,that a user of the user device is viewing a second content item that isrelated to the first content item based at least in part on the storedmetadata; in response to determining that the user of the user device isviewing the second content item that is related to the first contentitem, determining, using a hardware processor, a probability value thatindicates a likelihood that the user would be interested in viewing thefirst content item; and in response to determining that the probabilityvalue is greater than a predetermined threshold value, causing aninterface that includes a reminder to view the first content item to bepresented on the user device.

In accordance with some embodiments of the disclosed subject matter, asystem for presenting a reminder to view content is provided, the systemcomprising: a hardware processor that is programmed to: determine that amessage in a communication interface that includes a link to a firstcontent item has been received by a user device; determine, at a firstpoint in time, whether the link to the content item has been selectedusing the user device; in response to determining that the link to thecontent item has not been selected, store metadata associated with thecontent item in association with an identifier of the user device;determine, at a second point in time, that a user of the user device isviewing a second content item that is related to the first content itembased at least in part on the stored metadata; in response todetermining that the user of the user device is viewing the secondcontent item that is related to the first content item, determine aprobability value that indicates a likelihood that the user would beinterested in viewing the first content item; and in response todetermining that the probability value is greater than a predeterminedthreshold value, cause an interface that includes a reminder to view thefirst content item to be presented on the user device.

In accordance with some embodiments of the disclosed subject matter, anon-transitory computer-readable medium containing computer-executableinstructions that, when executed by a processor, cause the processor toperform a method for presenting a reminder to view content is provided.The method comprises: determining that a message in a communicationinterface that includes a link to a first content item has been receivedby a user device; determining, at a first point in time, whether thelink to the content item has been selected using the user device; inresponse to determining that the link to the content item has not beenselected, storing metadata associated with the content item inassociation with an identifier of the user device; determining, at asecond point in time, that a user of the user device is viewing a secondcontent item that is related to the first content item based at least inpart on the stored metadata; in response to determining that the user ofthe user device is viewing the second content item that is related tothe first content item, determining a probability value that indicates alikelihood that the user would be interested in viewing the firstcontent item; and in response to determining that the probability valueis greater than a predetermined threshold value, causing an interfacethat includes a reminder to view the first content item to be presentedon the user device.

In accordance with some embodiments of the disclosed subject matter, asystem for presenting a reminder to view content is provided, the systemcomprising: means for determining that a message in a communicationinterface that includes a link to a first content item has been receivedby a user device; means for determining, at a first point in time,whether the link to the content item has been selected using the userdevice; in response to determining that the link to the content item hasnot been selected, means for storing metadata associated with thecontent item in association with an identifier of the user device; meansfor determining, at a second point in time, that a user of the userdevice is viewing a second content item that is related to the firstcontent item based at least in part on the stored metadata; in responseto determining that the user of the user device is viewing the secondcontent item that is related to the first content item, means fordetermining a probability value that indicates a likelihood that theuser would be interested in viewing the first content item; and inresponse to determining that the probability value is greater than apredetermined threshold value, means for causing an interface thatincludes a reminder to view the first content item to be presented onthe user device.

In some embodiments, the first content item is a video, and theinterface that includes the reminder to view the first content itemincludes a queue of related videos.

In some embodiments, the interface includes a link to the first contentitem.

In some embodiments, the probability value is determined based at leastin part on a duration of time between the first point in time and thesecond point in time.

In some embodiments, the system further comprises means for determininga type of interface that includes the reminder based at least in part onthe probability value.

In some embodiments, the system further comprises means for determiningthat the second content item is related to the first content item basedat least in part on a source of the first content item and the secondcontent item.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, features, and advantages of the disclosed subjectmatter can be more fully appreciated with reference to the followingdetailed description of the disclosed subject matter when considered inconnection with the following drawings, in which like reference numeralsidentify like elements.

FIG. 1 shows a schematic diagram of an example of a system forpresenting a reminder to view content in accordance with someembodiments of the disclosed subject matter.

FIG. 2 shows an example of hardware that can be used in a server and/ora user device in accordance with some embodiments of the disclosedsubject matter.

FIG. 3 shows an example of an information flow diagram for presenting areminder to view content in accordance with some embodiments of thedisclosed subject matter.

FIG. 4 shows an example of a process for presenting a reminder to viewcontent in accordance with some embodiments of the disclosed subjectmatter.

FIGS. 5A and 5B show examples of user interfaces for receiving a link toa video and presenting a reminder to view the video in accordance withsome embodiments of the disclosed subject matter.

DETAILED DESCRIPTION

In accordance with various embodiments, mechanisms (which can includemethods, systems, and media) for presenting a reminder to view contentare provided.

In some embodiments, the mechanisms described herein can receive, on auser device, a message that includes a link to a content item (e.g., avideo, a web page, a news article, and/or any other suitable type ofcontent item). The mechanisms can then determine whether or not the linkwas selected, for example, within a particular period of time. If it isdetermined that the link was not selected, the mechanisms can cause areminder to view the content item to be presented on the user device.

In some embodiments, the mechanisms can additionally determine whetheror not to present a reminder to view the content item based on anysuitable information. For example, in some embodiments, the mechanismscan determine that a reminder is to be presented in response todetermining that a user of the user device is currently viewing arelated content item (e.g., a content item associated with the samecontent source, a content item related to a similar topic, and/orrelated in any other suitable manner). As a more particular example, insome embodiments, the related content item can be a video that isrelated (e.g., by topic, by creator, by content source, and/or relatedin any other suitable manner) to the content item corresponding to thelink. As another more particular example, in instances where the contentitem corresponding to the link is an article published by a particularsource, the related content item can be a second article that ispublished by the same source.

In some embodiments, the reminder can be presented using any suitablemodality, such as a text message, a push notification, within a userinterface indicating a playlist of content items, within a userinterface that includes other information (e.g., current weather and/ortraffic conditions), and/or in any other suitable manner. In someembodiments, the modality used to present the reminder can be determinedbased on a probability that the user is likely to be interested inviewing the content associated with the link. For example, in instanceswhere the probability is greater than a predetermined threshold value,the reminder can be presented using a relatively intrusive modality,such as a text message. Alternatively, in instances where theprobability is less than a predetermined threshold value, the remindercan be presented using a relatively non-intrusive type of message, suchas within a user interface that indicates a playlist of content items.

In some embodiments, a user can affirmatively provide consent forparticular types of information to be used. For example, in someembodiments, a user can provide consent to retrieve information fromparticular sources (e.g., social networking services, a user accountassociated with a video hosting service, the user's e-mail account,and/or any other suitable source of information) to be used to determinethe probability that the user is interested in viewing the videocorresponding to the received link. In some embodiments, the user canselect and/or deselect particular sources of information at any suitabletime.

Turning to FIG. 1, an example 100 of hardware for presenting a reminderto view content that can be used in accordance with some embodiments ofthe disclosed subject matter is shown. As illustrated, hardware 100 caninclude one or more servers, such as a content server 102, a data server104, a communication network 106, and one or more user devices 108.

Content server 102 can be any suitable server for storing content anddelivering the content to a user device 108 in some embodiments. Forexample, content server 102 can be a server that streams media contentto user device 108 via communication network 106. As a more particularexample, in some embodiments, content server 102 can stream mediacontent to user device 108 in response to receiving a request for themedia content from user device 108. Content provided by content server102 can be any suitable content, such as video content, audio content,television programs, movies, cartoons, sound effects, audiobooks, webpages, news articles, streaming live content (e.g., a streaming radioshow, a live concert, and/or any other suitable type of streaming livecontent), electronic books, search results and/or any other suitabletype of content. Content can be created and uploaded to content server102 by any suitable entity.

Data server 104 can be any suitable server for storing informationrelated to a user's preferences for viewing content, information relatedto content a user has previously watched, and/or any other suitableinformation. In some embodiments, data server 104 can transmit, to auser device, information related to content the user has previouslywatched, as described below in connection with FIG. 3. For example, insome embodiments, data server 104 can transmit information indicatingthat the content item associated with the link has already been viewedfrom a user account associated with the user device. As another example,in some embodiments, data server 104 can transmit information indicatingthat a content item similar to the content item associated with the link(e.g., based on metadata associated with the two content items, based onidentities of the creators of the two content items, based on commonviewers of the two content items, and/or based on any other suitableinformation) has been viewed from a user account associated with theuser device. Note that, in some embodiments, authorization can berequested from a user before information relating to the user'spreferences and/or content viewing habits is stored on data server 104.

Communication network 106 can be any suitable combination of one or morewired and/or wireless networks in some embodiments. For example,communication network 106 can include any one or more of the Internet, amobile data network, a satellite network, a local area network, a widearea network, a telephone network, a cable television network, a WiFinetwork, a WiMax network, and/or any other suitable communicationnetwork.

User device(s) 108 can include any one or more user devices suitable forreceiving messages and/or presenting content. For example, in someembodiments, user device(s) 108 can include mobile devices, such as amobile phone, a tablet computer, a laptop computer, a vehicle (e.g., acar, a boat, an airplane, or any other suitable vehicle) entertainmentsystem, a portable media player, or any other suitable mobile device. Asanother example, in some embodiments, user device(s) 108 can includenon-mobile devices such as a desktop computer, a set-top box, atelevision, a streaming media player, a game console, or any othersuitable non-mobile device.

Although content server 102 and data server 104 are illustrated asseparate devices, any one or more of these devices can be combined intoone device in some embodiments. Also, although only one each of contentserver 102 and data server 104 are shown in FIG. 1 to avoidover-complicating the figure, any suitable one or more of each devicecan be used in some embodiments.

Although only one user device 108 is shown in FIG. 1 to avoidover-complicating the figure, any suitable number of each of thesedevices, and any suitable types of these devices, can be used in someembodiments.

Content server 102, data server 104, and user device 108 can beimplemented using any suitable hardware in some embodiments. Forexample, in some embodiments, devices 102, 104, and 108 can beimplemented using any suitable general purpose computer or specialpurpose computer. For example, a server may be implemented using aspecial purpose computer. Any such general purpose computer or specialpurpose computer can include any suitable hardware. For example, asillustrated in example hardware 200 of FIG. 2, such hardware can includehardware processor 202, memory and/or storage 204, an input devicecontroller 206, an input device 208, display/audio drivers 210, displayand audio output circuitry 212, communication interface(s) 214, anantenna 216, and a bus 218.

Hardware processor 202 can include any suitable hardware processor, suchas a microprocessor, a micro-controller, digital signal processor(s),dedicated logic, and/or any other suitable circuitry for controlling thefunctioning of a general purpose computer or a special purpose computerin some embodiments.

Memory and/or storage 204 can be any suitable memory and/or storage forstoring programs, data, media content, and/or any other suitableinformation in some embodiments. For example, memory and/or storage 204can include random access memory, read-only memory, flash memory, harddisk storage, optical media, and/or any other suitable memory.

Input device controller 206 can be any suitable circuitry forcontrolling and receiving input from one or more input devices 208 insome embodiments. For example, input device controller 206 can becircuitry for receiving input from a touch screen, from one or morebuttons, from a voice recognition circuit, from a microphone, from acamera, from an optical sensor, from an accelerometer, from atemperature sensor, from a near field sensor, and/or any other type ofinput device.

Display/audio drivers 210 can be any suitable circuitry for controllingand driving output to one or more display/audio output circuitries 212in some embodiments. For example, display/audio drivers 210 can becircuitry for driving an LCD display, a speaker, an LED, or any othertype of output device.

Communication interface(s) 214 can be any suitable circuitry forinterfacing with one or more communication networks, such as network 106as shown in FIG. 1. For example, interface(s) 214 can include networkinterface card circuitry, wireless communication circuitry, and/or anyother suitable type of communication network circuitry.

Antenna 216 can be any suitable one or more antennas for wirelesslycommunicating with a communication network in some embodiments. In someembodiments, antenna 216 can be omitted when not needed.

Bus 218 can be any suitable mechanism for communicating between two ormore components 202, 204, 206, 210, and 214 in some embodiments.

Any other suitable components can be included in hardware 200 inaccordance with some embodiments.

Turning to FIG. 3, an example 300 of an information flow diagram forpresenting a reminder to view content is shown in accordance with someembodiments of the disclosed subject matter. As illustrated, blocks ofinformation flow diagram 300 can be implemented on a first user device,a second user device, content server 102, and/or data server 104.

At 302, the first user device can transmit a message that includes alink to a content item (e.g., a video, a television program, an e-book,a news article, a web page, and/or any other suitable type of content).In some embodiments, the message can include any suitable type ofcommunication, such as a text message, an e-mail, a chat and/or aninstant message, a comment on a post on a social networking site, a tagthat indicates a user of the second user device on a post on a socialnetworking site that includes the link to the content item, and/or anyother suitable type of message. In some embodiments, the message caninclude any other suitable content, such as text, images, icons,graphics, animations, and/or any other suitable content.

At 304, the second user device can receive the message. In someembodiments, the message can be displayed by the second user device uponreceipt. Alternatively, in some embodiments, the second user device cancause a notification of the received message to be presented, and cancause the message to be presented in response to determining that anindication to present the message has been received (e.g., bydetermining that the notification has been selected, by determining thatan application associated with a particular type of message has beenselected, and/or based on any other suitable type of indication). FIG.5A shows an example of a user interface for presenting the receivedmessage on the second user device.

At 306, the second user device can determine whether the link in thereceived message has been selected. In some embodiments, the second userdevice can use any suitable technique(s) to determine whether the linkhas been selected. For example, in some embodiments, the second userdevice can determine if a web page corresponding to the link has beenopened on the user device. As another example, in some embodiments, thesecond user device can determine if the message was closed or dismissedwithout the link having been selected. In some embodiments, the seconduser device can determine if the link was selected and/or if the messagewas closed within a predetermined period of time (e.g., within twominutes of the message being received and/or opened, within ten minutesof the message being received and/or opened, within twenty minutes ofthe message being received and/or opened, and/or any other suitable timeperiod).

If, at 306, it is determined that the link has been selected (“yes” at306), content server 102 can cause the content item associated with thelink to be presented on the second user device at 308. For example, insome embodiments, content server 102 can cause the content item to betransmitted to the second user device via communication network 106.

If, at 306, it is determined that the link has not been selected (“no”at 306), data server 104 can store metadata associated with the contentitem and an identifier of the second user device at 310. In someembodiments, the identifier of the second user device can be based onany suitable information, such as a username associated with a useraccount authenticated on the second user device, a device typeassociated with the second user device, and/or any other suitableinformation. In some embodiments, the metadata associated with thecontent item can indicate any suitable information, such as a title ofthe content item, an author and/or creator of the content item, a dateof publication and/or creation of the content item, one or more topicsassociated with the content item, one or more keywords associated withthe content item, a name of a content sharing service and/or web site onwhich the content item is stored, and/or any other suitable information.

At 312, data server 104 can determine whether a reminder to view thecontent item is to be presented on the second user device. In someembodiments, data server 104 can determine whether the reminder is to bepresented at any suitable time after the message including the link tothe content item was received by the second user device (e.g., a daylater, two days later, a week later, and/or any other suitable timeperiod). In some embodiments, data server 104 can determine whether thereminder is to be presented based on any suitable information and usingany suitable technique(s). For example, in some embodiments, thedetermination can be made based on a duration of time elapsed since themessage was received by the second user device, recent content accessedby the second user device, and/or any other suitable information. A moreparticular example of a process for determining whether a reminder is tobe presented on the second user device is shown in and described belowin connection with FIG. 4.

Note that, in some embodiments, process 300 can first determine whetherthe second user device is accessing content related to the content itemcorresponding to the link included in the message received at block 304,and can determine whether the reminder to view the content item is to bepresented in response to determining that related content is currentlybeing accessed on the second user device. Process 300 can determine thatrelated content is being accessed using any suitable information, forexample, the metadata stored at block 310, information indicating asource of the content item and/or currently accessed content, and/or anyother suitable information. A more particular example of techniques fordetermining whether currently accessed content is related to the contentitem corresponding to the link is described below in connection withblock 402 of FIG. 4.

If, at 312, data server 104 determines that no reminder is to bepresented on the second user device (“no” at 312), information flowdiagram 300 can end at 318.

If, at 312, data server 104 determines that a reminder is to bepresented on the second user device (“yes” at 312), data server 104 cantransmit instructions to present the reminder on the second user deviceat 314. In some embodiments, the reminder can be presented in anysuitable manner. For example, in some embodiments, the reminder can bepresented as an indication that a user associated with the first userdevice recommended the content item. As a more particular example, insome embodiments, the reminder can be presented in a user interface thatincludes a group of content that is recommended for a user of the seconduser device and/or a queue of content that will be automaticallypresented on the second user device, as shown in and described below inconnection with FIG. 5B. As another more particular example, in someembodiments, the reminder can be included in a push notificationpresented on the second user device. As yet another more particularexample, in some embodiments, the reminder can be presented within auser interface presented on the second user device that additionallyincludes any other suitable information, such as local trafficconditions, local weather conditions, other reminders (e.g., remindersof upcoming meetings, and/or any other suitable reminders), and/or anyother suitable information.

In some embodiments, data server 104 can determine a type of format(e.g., presented within a push notification, presented within a userinterface indicating other recommended content, and/or any othersuitable type of format as described above) using any suitabletechnique(s) and any suitable information. For example, in someembodiments, if the content associated with the link is a video contentitem hosted on a particular video sharing service, data server 104 candetermine that the reminder is to be presented in connection with a userinterface indicating content that is to be automatically presented inconnection with the video sharing service, as shown in and describedbelow in connection with FIG. 5B. As another example, in someembodiments, data server 104 can determine the type of format based onuser preferences. As a more particular example, if data server 104determines that a user is likely to view push notifications and/orselect content indicated in a push notification, data server 104 candetermine that the reminder is to be presented within a pushnotification. As another more particular example, if data server 104determines that a user of the second user device frequently dismissesand/or closes interfaces of a particular type of message format withoutviewing the message or selecting links included in the message, dataserver 104 can determine that particular type of message format is notto be used in connection with the reminder.

At 316, the second user device can receive the transmitted instructionsfrom data server 104, and can cause the reminder to view the contentitem to be presented. A more particular example of a user interface thatincludes a reminder to view a content item is shown in and describedbelow in connection with FIG. 5B.

Information flow diagram 300 can end at 318.

Turning to FIG. 4, an example 400 of a process for determining whetherto present a reminder to view a content item is shown in accordance withsome embodiments of the disclosed subject matter. In some embodiments,blocks of process 400 can be implemented on content server 102 and/ordata server 104.

Process 400 can begin at 402 by receiving information indicating that auser device that received a message that includes a link to a contentitem (e.g., the second user device shown in and described above inconnection with FIG. 3) is accessing content similar to the content itemcorresponding to the link. The related content can be related to thecontent item in any suitable manner. For example, in some embodiments, acontent type associated with the accessed content can be the same as thecontent type associated with the content item corresponding to the link.As a more particular example, in some embodiments, both content itemscan be videos, television programs, movies, e-books, articles, and/orany other suitable type of content. As another example, in someembodiments, the accessed content can be associated with the same sourceas the content item corresponding to the link. As a more particularexample, in some embodiments, both content items can be hosted on thesame content sharing service, hosted by the same website, shared in thesame group on a social networking service, published by the same entity(e.g., the same online newspaper, the same blog, and/or any othersuitable entity), and/or any other suitable source of content. As yetanother example, in some embodiments, the accessed content can berelated to a similar topic as the content item corresponding to thelink. As a more particular example, in some embodiments, both contentitems can be associated with one or more similar keywords that indicatetopics of the content items.

Process 400 can determine that related content is being accessed usingany suitable technique(s). For example, in some embodiments, process 400can identify the content that is being accessed based on activitiesassociated with a user account authenticated with the user devicecorresponding to a content sharing service and/or a social networkingservice. As a more particular example, in some embodiments, process 400can identify media content hosted on a particular video sharing servicethat is currently being viewed by a user associated with the useraccount. As another example, in some embodiments, process 400 canidentify the content based on a URL and/or a website that is currentlybeing accessed by the user device. As yet another example, in someembodiments, process 400 can determine if the accessed content isrelated to the content item corresponding to the link based on themetadata associated with the content item identified and stored inassociation with an identifier of a user account corresponding to thereceived message, as shown in and described above in connection withblock 310 of FIG. 3.

Process 400 can receive information indicating intent of a user to viewthe content item corresponding to the link in the message received bythe user device at 404. In some embodiments, the information can bebased on the user's previous responses to messages received from thesender. For example, in some embodiments, process 400 can determine aproportion of previously received links to content received from thesame sender that have been selected by the user. As a more particularexample, in some embodiments, process 400 can determine that the user ismore likely to intend to view the content item in instances where theuser has previously selected links received from the sender. As aspecific example, process 400 can estimate a likelihood that the userintends to view the content item based on a proportion of links receivedfrom the sender that the user has previously selected. As anotherexample, in some embodiments, process 400 can estimate a strength of arelationship between the recipient of the message and the sender of themessage, based on any suitable information, such as a number of groupsboth users belong to in a social networking site, a number of messagesexchanged between the two users, a frequency at which messages have beenexchanged between the two users, and/or any other suitable information.As a more particular example, in some embodiments, process 400 candetermine that the user is more likely to intend to view the contentitem in instances where the strength of the relationship between theuser and the send of the message is relatively high. As yet anotherexample, in instances where the user has provided consent, process 400can determine that the user is more likely to intend to view the contentitem in instances where the user has sent a positive message in reply tothe received message. As a more particular example, in some embodiments,process 400 can parse the message sent in reply for words and/or phrasesindicating an intent to view the content item in the future (e.g.,“looks interesting,” “I'll look at that later tonight,” and/or any othersuitable words or phrases).

At 406, process 400 can receive information indicating a source of therelated content being accessed at 402. For example, as described abovein connection with block 402, process 400 can identify a name of awebsite, a name of a publication, a name of content sharing service, aname of a creator of the content, and/or any other suitable entityassociated with the related content.

Process 400 can receive information indicating a duration of time (e.g.,an hour, a day, a week, and/or any other suitable duration of time)elapsed since the message was received by the user device at 408. Forexample, in some embodiments, process 400 can determine an elapsed timebetween the time the message was received and a current point in time.

Process 400 can determine a probability value that indicates whether auser of the user device would be interested in viewing the content itembased on the information received at blocks 402-408. The information canbe combined in any suitable manner to calculate the probability value.For example, in some embodiments, information from different factors(e.g., information indicating user intent, information indicating asource of the content, a duration of elapsed time since the message wasreceived, and/or any other suitable factors) can be indicated by ascore, and the scores associated with each factor can be combined usingany suitable technique(s) (e.g., a weighted average of the scores,and/or any other suitable technique).

As a particular example, in some embodiments, process 400 can determinethat there is a relatively high likelihood of the user being interestedin viewing the content item in instances where there is a relativelystrong relationship between the user and the sender of the message. Asanother particular example, in some embodiments, process 400 candetermine that there is a relatively low likelihood of the user beinginterested in viewing the content in instances where the duration ofelapsed time since the message was received exceeds a predeterminedthreshold (e.g., received more than a week ago, received more than amonth ago, and/or any other suitable time period). As yet anotherparticular example, in some embodiments, process 400 can determine thatthere is a relatively high likelihood of the user being interested inviewing the content if a relevance score of content currently beingaccessed to the content item associated with the message exceeds apredetermined threshold. Note that, in such embodiments, the relevancescore can be calculated based on any suitable information, such asmetadata indicating a source of the content, a creator of the content,keywords associated with the content, and/or any other suitableinformation. Additionally, note that, in some embodiments, likelihoodsof the user being interested in viewing the content that are calculatedbased on different factors can be combined in any suitable manner (e.g.,a weighted average). In some embodiments, weights associated with eachfactor can be modified over time, for example, based on whether the userviews the content item after receiving the reminder.

Note that, in some embodiments, any other suitable information can beused by process 400 to calculate the probability value indicating thelikelihood of the user being interested in view the content item. Forexample, in some embodiments, process 400 can use information indicatingpopularity of the content item (e.g., a number of times the content itemhas been viewed, a number of times the content item has been shared on asocial networking site, a number of time the content item has beencommented on, and/or any other suitable metric) to calculate theprobability value. As another example, in some embodiments, process 400can determine popularity information particular to connections of theuser on a social networking site. As a more particular example, process400 can determine a number of connections of the user that have viewed,endorsed, shared, and/or commented on the content item.

At 412, process 400 can determine whether the probability valuecalculated at block 410 exceeds a predetermined threshold value. In someembodiments, the predetermined threshold value can be any suitable value(e.g., 0.3, 0.5, 0.75, 0.9, and/or any other suitable value).

If, at 412, it is determined that the probability value does not exceedthe predetermined threshold value (“no” at 412), process 400 can end at414.

If, at 412, it is determined that the probability value exceeds thepredetermined threshold value (“yes” at 412), process 400 can transmitinstructions to present a reminder to view the content item to the userdevice at 416. As described above in connection with FIG. 3, theinstructions can cause the reminder to be presented in any suitablemanner. For example, in some embodiments, the instructions can cause thereminder to be presented as a push notification, in a text message, in auser interface that includes any other suitable content (e.g.,information indicating weather, traffic, other reminders, and/or anyother suitable content), in a user interface that indicates content thatwill be automatically played in a playlist (e.g., as shown in anddescribed below in connection with FIG. 5B), in a user interface thatindicates content that is recommended for the user, and/or in any othersuitable manner.

Note that, in some embodiments, prior to transmitting the instructionsto present the reminder to view the content item, process 400 candetermine the manner in which the reminder is to be presented. In somesuch embodiments, the manner of presentation can be determined based onany suitable information. For example, in some embodiments, the mannerof presentation can be determined based on the probability valuecalculated at block 410. As a more particular example, process 400 canselect a particular type of notification (e.g., a text message and/orpush notification) if the probability value is greater than apredetermined threshold value (e.g., greater than 0.8), indicating thatthere is a high likelihood that the user will want to watch the videoafter receiving the reminder. As another more particular example,process 400 can select a different type of notification (e.g., areminder within a user interface indicating a queue of content items) ifthe probability value is within a particular range (e.g., between 0.5and 0.6, and/or any other suitable range).

As another example, in some embodiments, the manner of presentation canbe determined based on information indicating a user's previous actionsin response to receiving notifications of different modalities. As amore particular example, in instances where it is determined that a userfrequently selects links included in push notifications, process 400 candetermine that the reminder is to be included in a push notification.Note that, in some embodiments, any suitable factors used to determinethe manner in which the reminder is to be presented can be updated overtime based on a user's actions in response to receiving previousreminders of content to view.

As yet another example, in some embodiments, the manner of presentationof the reminder can be determined based on a type of content associatedwith the content item. As a more particular example, in instances wherethe type of content includes video content and/or audio content, thereminder can be presented in connection with a user interface thatincludes suggested content and/or content that is in a queue that willbe presented automatically (e.g., a playlist). As another moreparticular example, in instances where the type of content includesprimarily still content (e.g., a link to a website, a news article,and/or any other suitable type of content), the reminder can bepresented in a text message and/or a push notification).

Note that, in some embodiments, process 400 can determine the manner ofpresentation of the reminder using any suitable combination ofinformation (e.g., the probability value, the user's previous actions,the type of content, and/or any other suitable information), and theinformation can be combined in any suitable manner.

Turning to FIG. 5A, an example 500 of a user interface for presenting areceived message that includes a link to a video is shown in accordancewith some embodiments of the disclosed subject matter. As illustrated,user interface 500 can include a sender name 502, a message timestamp504, a message 506, and a link 508.

Sender name 502 can include an indication of an identity of the senderof message 506. For example, as shown in FIG. 5A, sender name 502 caninclude text that indicates the identity of the sender. In someembodiments, sender name 502 can include any suitable images, icons,graphics, animations, and/or any other suitable content. In someembodiments, sender name 502 can be omitted.

Message timestamp 504 can include any indication of a time that message506 was received. For example, as shown in FIG. 5A, message timestamp504 can include a date and/or a time of day. In some embodiments,message timestamp 504 can be omitted.

As described above in connection with FIGS. 3 and 4, message 506 can bea message of any communication type. In some embodiments, message 506can include link 508 as well as any other suitable content, such astext, images, icons, graphics, animations, and/or any other suitablecontent. Link 508 can be a link to media content, such as a video. Insome embodiments, link 508 can be a hyperlink to any suitable web siteand/or media content hosting service. In some embodiments, link 508 canbe hidden, and a particular image and/or word(s) of message 506 can behyperlinked to the video.

Turning to FIG. 5B, an example 550 of a user interface that includes areminder to view the media content item corresponding to a link includedin a message is shown in accordance with some embodiments of thedisclosed subject matter. As shown, user interface 550 can include videocontent 552 and a playlist panel 554.

Video content 552 can be any suitable presentation of video content. Insome embodiments, video content 552 can be presented within a videoplayer window, which can include any suitable video player controls,such as a pause input, a rewind input, a fast-forward input, a volumecontrol, and/or any other suitable controls.

Playlist panel 554 can be any suitable user interface for indicatingcontent that will begin being presented. For example, in someembodiments, playlist panel 554 can indicate content that was aggregatedinto a user-created playlist. As another example, in some embodiments,playlist panel 554 can indicate content that was identified as relatedto video content 554 and will begin playing automatically afterpresentation of video content 554 finishes. Note that, in someembodiments, playlist panel 554 can be omitted. Additionally oralternatively, in some embodiments, a panel indicating content that isrecommended for the user (e.g., based on video content 554, and/or basedon any other suitable information) can be presented in user interface550.

Playlist panel 554 can include indications of one or more media contentitems, such as videos 556 and 558. In some embodiments, each indicationcan include any suitable information, such as a name of the mediacontent, a creator of the media content, a date of creation of the mediacontent, an image associated with the media content, and/or any othersuitable information. In some embodiments, a video (e.g., video 558)corresponding to link 508 (included in message 506, as shown in anddescribed above in connection with FIG. 5A) can be presented with areminder, such as reminder 560. As shown in FIG. 5B, reminder 560 caninclude any suitable information, such as a name of a sender of message506, a date on which message 506 was sent, an amount of time elapsedsince message 506 was sent, a modality by which message 506 was sent, animage associated with the sender of message 506, and/or any othersuitable information.

It should be understood that at least some of the above described blocksof the processes of FIGS. 3 and 4 can be executed or performed in anyorder or sequence not limited to the order and sequence shown in anddescribed in the figure. Also, some of the above blocks of the processesof FIGS. 3 and 4 can be executed or performed substantiallysimultaneously where appropriate or in parallel to reduce latency andprocessing times. Additionally or alternatively, some of the abovedescribed blocks of the processes of FIGS. 3 and 4 can be omitted.

In some embodiments, any suitable computer readable media can be usedfor storing instructions for performing the functions and/or processesherein. For example, in some embodiments, computer readable media can betransitory or non-transitory. For example, non-transitory computerreadable media can include media such as magnetic media (such as harddisks, floppy disks, and/or any other suitable magnetic media), opticalmedia (such as compact discs, digital video discs, Blu-ray discs, and/orany other suitable optical media), semiconductor media (such as flashmemory, electrically programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), and/or any othersuitable semiconductor media), any suitable media that is not fleetingor devoid of any semblance of permanence during transmission, and/or anysuitable tangible media. As another example, transitory computerreadable media can include signals on networks, in wires, conductors,optical fibers, circuits, any suitable media that is fleeting and devoidof any semblance of permanence during transmission, and/or any suitableintangible media.

In situations in which the systems described here collect personalinformation about users, or make use of personal information, the usersmay be provided with an opportunity to control whether programs orfeatures collect user information (e.g., information about a user'ssocial network, social actions or activities, profession, a user'spreferences, or a user's current location). In addition, certain datamay be treated in one or more ways before it is stored or used, so thatpersonally identifiable information is removed. For example, a user'sidentity may be treated so that no personally identifiable informationcan be determined for the user, or a user's geographic location may begeneralized where location information is obtained (such as to a city,ZIP code, or state level), so that a particular location of a usercannot be determined. Thus, the user may have control over howinformation is collected about the user and used by a content server.

Accordingly, methods, systems, and media for presenting a reminder toview content are provided.

Although the invention has been described and illustrated in theforegoing illustrative embodiments, it is understood that the presentdisclosure has been made only by way of example, and that numerouschanges in the details of implementation of the invention can be madewithout departing from the spirit and scope of the invention, which islimited only by the claims that follow. Features of the disclosedembodiments can be combined and rearranged in various ways.

What is claimed is:
 1. A method for presenting a reminder to viewcontent, comprising: determining, at a first point in time, whether alink to a first content item in a message presented within acommunication interface has been selected using a user device;determining, at a second point in time, that a user of the user deviceis viewing a second content item that is related to the first contentitem; and in response to determining that the link to the first contenthas not been selected at the first point in time and in response todetermining that the user of the user device is viewing the secondcontent item that is related to the first content item at the secondpoint in time, causing an interface that that is presented along withthe second content item, wherein the interface includes a queue ofrelated content items including the first content item.
 2. The method ofclaim 1, wherein the first content item in the queue of related contentitems includes a notification that includes at least a user identifierof a sharing user that shared the first content item and a link to thefirst content item.
 3. The method of claim 2, wherein the notificationfurther includes a modality in which the message was sent and timinginformation associated with when the message was sent.
 4. The method ofclaim 1, further comprising, in response to determining that the link tothe first content item has not been selected, storing metadataassociated with the content item in association with an identifier ofthe user device, wherein the user of the user device is determined asviewing the second content item based at least in part on the storedmetadata.
 5. The method of claim 1, further comprising determining aprobability value that indicates a likelihood that the user would beinterested in viewing the first content item, wherein the interface ispresented along with the second content item in response to determiningthat the probability value is greater than a predetermined thresholdvalue.
 6. The method of claim 5, wherein the probability value isdetermined based at least in part on a duration of time between thefirst point in time and the second point in time.
 7. The method of claim5, further comprising selecting a particular type of the notificationbased at least in part on the probability value.
 8. The method of claim1, wherein the second content item is determined as being related to thefirst content item based at least in part on a source of the firstcontent item and the second content item.
 9. The method of claim 1,further comprising determining that the message in the communicationinterface that includes the link to a first content item has beenreceived by the user device.
 10. A system for presenting a reminder toview content, the system comprising: a hardware processor that isprogrammed to: determine, at a first point in time, whether a link to afirst content item in a message presented within a communicationinterface has been selected using a user device; determine, at a secondpoint in time, that a user of the user device is viewing a secondcontent item that is related to the first content item; and in responseto determining that the link to the first content has not been selectedat the first point in time and in response to determining that the userof the user device is viewing the second content item that is related tothe first content item at the second point in time, cause an interfacethat that is presented along with the second content item, wherein theinterface includes a queue of related content items including the firstcontent item.
 11. The system of claim 10, wherein the first content itemin the queue of related content items includes a notification thatincludes at least a user identifier of a sharing user that shared thefirst content item and a link to the first content item.
 12. The systemof claim 11, wherein the notification further includes a modality inwhich the message was sent and timing information associated with whenthe message was sent.
 13. The system of claim 10, wherein the hardwareprocessor is further programmed to, in response to determining that thelink to the first content item has not been selected, store metadataassociated with the content item in association with an identifier ofthe user device, wherein the user of the user device is determined asviewing the second content item based at least in part on the storedmetadata.
 14. The system of claim 10, wherein the hardware processor isfurther programmed to determine a probability value that indicates alikelihood that the user would be interested in viewing the firstcontent item, wherein the interface is presented along with the secondcontent item in response to determining that the probability value isgreater than a predetermined threshold value.
 15. The system of claim14, wherein the probability value is determined based at least in parton a duration of time between the first point in time and the secondpoint in time.
 16. The system of claim 14, wherein the hardwareprocessor is further programmed to select a particular type of thenotification based at least in part on the probability value.
 17. Thesystem of claim 10, wherein the second content item is determined asbeing related to the first content item based at least in part on asource of the first content item and the second content item.
 18. Anon-transitory computer-readable medium containing computer executableinstructions that, when executed by a processor, cause the processor toperform a method for presenting a reminder to view content, the methodcomprising: determining, at a first point in time, whether a link to afirst content item in a message presented within a communicationinterface has been selected using a user device; determining, at asecond point in time, that a user of the user device is viewing a secondcontent item that is related to the first content item; and in responseto determining that the link to the first content has not been selectedat the first point in time and in response to determining that the userof the user device is viewing the second content item that is related tothe first content item at the second point in time, causing an interfacethat that is presented along with the second content item, wherein theinterface includes a queue of related content items including the firstcontent item.